Skip to content

HY/CRTX-240386/Telemetry-Failures-CortexUpdateCase#44281

Open
hyaffe839 wants to merge 3 commits into
masterfrom
HY/CRTX-240386/Telemetry-Failures-CortexUpdateCase
Open

HY/CRTX-240386/Telemetry-Failures-CortexUpdateCase#44281
hyaffe839 wants to merge 3 commits into
masterfrom
HY/CRTX-240386/Telemetry-Failures-CortexUpdateCase

Conversation

@hyaffe839
Copy link
Copy Markdown
Contributor

@hyaffe839 hyaffe839 commented May 12, 2026

Contributing to Cortex XSOAR Content

Make sure to register your contribution by filling the contribution registration form

The Pull Request will be reviewed only after the contribution registration form is filled.

Status

  • In Progress
  • Ready
  • In Hold - (Reason for hold)

Related Issues

CRTX-240386

Description

Fixes telemetry failures in core-update-case command.

Must have

  • Tests
  • Documentation

@hyaffe839 hyaffe839 requested a review from JudahSchwartz as a code owner May 12, 2026 11:46
@hyaffe839 hyaffe839 self-assigned this May 12, 2026
@content-bot
Copy link
Copy Markdown
Contributor

content-bot commented May 12, 2026

🤖 AI-Powered Code Review Available

You can leverage AI-powered code review to assist with this PR!

Available Commands:

  • @marketplace-ai-reviewer start review - Initiate a full AI code review
  • @marketplace-ai-reviewer re-review - Incremental review for new commits

@github-actions
Copy link
Copy Markdown

github-actions Bot commented May 12, 2026 •
edited
Loading

Coverage

Coverage Report
FileStmtsMissCoverMissing
Packs/Core/Integrations/CortexPlatformCore
   CortexPlatformCore.py203221489%515, 517, 519, 522, 582–583, 585–586, 588, 676, 679–681, 687–690, 692, 694, 707, 719, 733, 738, 752, 755, 762, 765, 772, 779, 786, 804, 812, 819, 826, 834, 839, 849–850, 865–866, 881, 888, 893, 896, 901, 914–915, 922, 928, 945, 965, 967, 987, 1003, 1010, 1017, 1020, 1029, 1045, 1060, 1072, 1079, 1086, 1093, 1100, 1113, 1118, 1131–1132, 1257, 1447–1448, 1527, 1530, 1532, 1662, 1712–1714, 1969–1970, 1975, 1977, 1979, 2019, 2022–2023, 2025–2026, 2165–2180, 2182, 2301–2302, 2479–2482, 2487–2488, 2493, 2498, 2503–2504, 2509–2513, 2515, 2531, 2545, 2552–2554, 2556, 2562, 2575–2579, 2586–2588, 2590, 2600, 2674–2676, 2683–2684, 2686–2691, 2693–2695, 2697, 2735, 2748, 2785, 2870, 3056–3061, 3063, 3124–3126, 3283–3284, 3387, 3483–3484, 3499–3500, 3526, 3544, 4013, 4015–4021, 4023, 4025, 4028–4031, 4033, 4058, 4060, 4072, 4100, 4103, 4108–4109, 4657, 4666, 4672–4674, 4712, 4771, 4855, 4892–4893, 5402, 6121, 6127
TOTAL203221489% 

Tests Skipped Failures Errors Time
464 0 💤 0 ❌ 0 🔥 7.529s ⏱️

@content-bot

This comment has been minimized.

Sign in to view
@content-bot
Copy link
Copy Markdown
Contributor

content-bot commented May 13, 2026

⚠️ The PR is missing the ready-for-pipeline-running label. Please add the label when the PR is ready in order to proceed.

@content-bot
Copy link
Copy Markdown
Contributor

content-bot commented May 13, 2026

Validate summary
The following errors were reported as warnings: GR110, PB130, PB131, MC101, RM108.
The following errors were thrown as a part of this pr: AS103.
The following errors can be ignored: AS103.
If the AG100 validation in the pre-commit GitHub Action fails, the pull request cannot be force-merged.

Verdict: PR can be force merged from validate perspective? ❌

@content-bot
Copy link
Copy Markdown
Contributor

content-bot commented May 13, 2026

🔍 AI Triage Report Available

An automated triage report has been generated for this pipeline.

Status: failed
Report ID: aeaa6e6d8ea240c9

📋 Triage Report
💡 Resolutions are available in the full report.

⚠️ AI-generated triage. Validate before acting.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@JudahSchwartz JudahSchwartz Awaiting requested review from JudahSchwartz JudahSchwartz is a code owner

At least 1 approving review is required to merge this pull request.

Assignees

@hyaffe839 hyaffe839

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@hyaffe839 @content-bot